close
authorJoey Hess <joeyh@joeyh.name>
Fri, 9 Sep 2022 18:53:26 +0000 (14:53 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 9 Sep 2022 18:53:26 +0000 (14:53 -0400)
doc/bugs/Files_recorded_with_other_file__39__s_checksums.mdwn
doc/bugs/Files_recorded_with_other_file__39__s_checksums/comment_7_d480e85683f0418441f26c7d61c4af02._comment [new file with mode: 0644]

index e74f155d8e51ad7a7cfeac7cc33029a191d78858..55dd7aa5e08aa41bc06582bd966583a2f966b779 100644 (file)
@@ -98,3 +98,5 @@ git config annex.diskreserve 100M
 
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
+> [[done]] since this has pretty strongly been confirmed to be a bug that
+> was already fixed in a newer git-annex version. --[[Joey]] 
diff --git a/doc/bugs/Files_recorded_with_other_file__39__s_checksums/comment_7_d480e85683f0418441f26c7d61c4af02._comment b/doc/bugs/Files_recorded_with_other_file__39__s_checksums/comment_7_d480e85683f0418441f26c7d61c4af02._comment
new file mode 100644 (file)
index 0000000..0d3ab40
--- /dev/null
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2022-09-09T18:50:43Z"
+ content="""
+Well, it seems that you have confirmed that the bug you were seeing is the
+known and already fixed problem involving files that had the same size and
+mtime.
+
+I suggest filing a new bug report for the other problem, since it does not
+seem like the same problem. I don't like to have to re-read long threads
+about unrelated problems to tease out the "current" problem than a bug
+report is talking about. 1 bug report per problem saves everyone time and
+confusion.
+"""]]